My HomeOps repository using kubernetes 💪

... managed with Flux, Renovate and GitHub Actions 🤖

Here, I perform DevOps best practices but at home. Check out the hardware section where I describe what sort of hardware I am using. Thanks to Ansible, it's very easy for me to manage my home infrastructure and the cluster. I try to adhere to Infrastructure as Code (IaC) and GitOps practices using tools like Terraform, Kubernetes, Flux, Renovate and GitHub Actions.

There is a template over at onedr0p/cluster-template if you wanted to try and follow along with some of the practices I use here.

For my cluster, I decided to use the PostgreSQL database instead of high IO load using etcd. I store critical data for my cluster in the PostgreSQL database and maintain it in High Availability mode. I use k3s deployed on ubuntu machines. For that I use ansible to prepare the machines and then install k3s and deploy my cluster configuration.

• cillium - CNI for k8s
• echo-server - REST Server Tests (Echo-Server) API (useful for debugging HTTP issues)
• longhorn - storage class provider for data persistence (yeah I'm giving longhorn second chance)
• k8s_gateway - DNS resolver for all types of external Kubernetes resources
• flux - GitOps tool for deploying manifests from the cluster directory
• kube-vip - layer 2 load balancer for the Kubernetes control plane
• cert-manager - SSL certificates - with Cloudflare DNS challenge
• traefik: Provides ingress cluster services.
• botkube Bot that helps me to monitor the cluster with notifications.
• hajimari - start page with ingress discovery
• reflector - mirror configmaps or secrets to other Kubernetes namespaces
• reloader - restart pods when Kubernetes configmap or secret changes
• system-upgrade-controller - upgrade k3s
• SOPS: Encrypts secrets which is safe to store - even to a public repository.

Flux watches my kubernetes folder (see Directories below) and makes the changes to my cluster based on the YAML manifests.

The way Flux works for me here is it will recursively search the kubernetes/apps folder until it finds the most top level kustomization.yaml per directory and then apply all the resources listed in it. That aforementioned kustomization.yaml will generally only have a namespace resource and one or many Flux kustomizations. Those Flux kustomizations will generally have a HelmRelease or other resources related to the application underneath it which will be applied.

Renovate watches my entire repository looking for dependency updates, when they are found a PR is automatically created. When some PRs are merged Flux applies the changes to my cluster.

This Git repository contains the following directories under kubernetes.

📁 kubernetes      # Kubernetes cluster defined as code
├─📁 bootstrap     # Flux installation
├─📁 flux          # Main Flux configuration of repository
└─📁 apps          # Apps deployed into my cluster grouped by namespace (see below)

My homelab runs on the following hardware (all k8s nodes are running on ubuntu 20.04):

Feel free to checkout my blog axell.dev which is also open source! I also have made a blog post about HW, what were my choices... which ones were good and which ones were bad. Click here.

I am proud to be a member of the home operations (previously k8s-at-home) community! I received a lot of help and inspiration for my Kubernetes cluster from this community which helped a lot. Thanks! ❤️

If you are interested in running your own k8s cluster at home, I highly recommend you to check out the k8s-at-home website.

Be sure to check out kubesearch.dev for ideas on how to deploy applications or get ideas on what you may deploy.

See LICENSE.